Preliminary Design
Requested by: Ms.
Kate Zimmerman
Academic
Program Administrator
Office
of Academic Affairs
Mr.
Brian Smith
College Webmaster
Office
of Enrollment and Planning Technology
Ms. Lisa Veino
Office of
Academic Affairs
Prepared by: Michael
Cervone, Web Designer
Thomas Hackett, Librarian
Sean
Hannon, Software Consultant
Sara
Pagliaro, Team Leader
John
Sawicki, Systems Administrator
E-mail: spartacus_computing@hotmail.com
Presentation information:
Roger
Bacon 328
Preliminary Design
Table of Contents
1. External Design
Specifications
Section
1:
User Displays and Report Formats
.
.. 3
Section
2:
User Command Summary
..
.. 29
Section
3:
Detailed Data Flow Diagrams
.. 32
Section
4:
Logical Data Dictionary
... 39
Section
5:
Logical Data Stores
.. 62
Section
6:
Logical Format of Data Files and Databases..
....
.. 91
2. Testing
Requirements:
Section
1:
GUI Testing
.
. 92
3. Appendices:
Appendix
A:
Gantt Chart.
.
. 93
Appendix
B:
Glossary of Terms
.... 94
1.1:
User Displays and Report Formats
Screen
for Any User
The login screen is the first screen that users will encounter. The login screen contains two fields: the username and the password. After the user enters their username and password into their respective fields, the system verifies the username and password to make sure they are valid before taking the user to their next respective screen.
Academic Affairs Screens
This page is the root page for the Academic Affairs administrator. The page contains links to the pages that allow the user to do various tasks; these links are Create or Edit Users, Check User Progress, Edit Catalog, Generate Publishers Copy, and View Current Catalog. The Generate Publishers Copy link when clicked compiles all of the catalog data into a document that can be sent electronically to the publisher. The View Current Catalog link when clicked opens up a new window with the current version of the catalog displayed. All other links are described on the following pages.
When the user clicks on the Create or Edit Users link (on the main Academic Affairs webpage), they are taken to this page, which displays links to other pages that allow the Academic Affairs administrator to perform various tasks on users.
These tasks include creating a new user. While creating the new user, the administrator must set a username, default password, update the new users e-mail, update his/her title and department, and set the permissions for the amount of information the user can access within the system.
The Academic Affairs administrator also has the ability to edit the information or privileges of any user that is currently a user within the system.
The Edit User Info page looks similar to the Create New User page since the same information can be edited.
The Academic Affairs system administrator also has the ability to remove any user from the system, allowing the administrator to keep an up-to-date list of all college staff that should have access to the College Catalog database.
When the user clicks the Check User Progress link (on the main Academic Affairs page), they will be taken to this page, which displays information relating to the progress of the other users of the system.
Since
the Academic Affairs system administrator has control over the editing done
throughout the entire catalog, the Edit
Catalog link on the main Academic Affairs administrator web page allows
him/her to access any part of the catalog for review or editing.
This is an example of a page that the Academic Affairs system administrator would have to review. The left hand side of the page is what the catalog looks like without the changes, while the right hand side of the page contains all revisions made by the system administrator.
Department
Head Screens
The Department Head home page contains links for all of the sections of the catalog that the given Department Head has access to change, along with corresponding check boxes (which signify if that particular section has been completed), and a link to view the course descriptions in their given department. Course descriptions can be read but not edited, since the information can only be changed in the Banner database system; our database system does not have the ability to change anything in Banner. When the Department Head is finished editing the section, s/he clicks the check box and click the Submit Changes button to submit his/her changes and update his/her catalog progress.
Using the example of Computer Science Department Head Scott Vandenberg, this would be an example of a section of the catalog that he would be able to edit. On this page, Dr. Vandenberg has the ability to edit faculty information. As with the Academic Affairs editing page, the left hand side is for review of what the catalog currently says without changes, while the right hand side contains all edited catalog information.
Another section of the catalog that Dr. Vandenberg would have the ability to edit is the Computer Science Departments information.
As stated previously, the Department Head has the ability to view course information, but does not have the ability to change any information contained within this section. This is an example of the Computer Science Departments course information.
Assistant
Dean Screens
This is an example of the Assistant Deans home page. It contains links to all of the different sections of the catalog that the Assistant Dean needs to change or monitor. The links include the following: Edit Given School General Information, View Progress, and Review/Edit Changes. When editing is completed the appropriate check box should be checked to indicate that the user is finished editing that section.
When clicked, the Edit Given School General Information link opens the general information section of the given school for editing.
The View Progress link from the Assistant Dean home page allows the Assistant Dean to view the editing progress of the Department Heads in their school.
The Review/Edit Changes link on the Assistant Dean home page allows the Assistant Dean to review and/or edit changes for the Department Heads within their school.
The Assistant Dean can review or edit all of the same information that Dr. Vandenberg (or any other Department Head within the school of science) can review or edit. This is a page containing Dr. Vandenbergs sections of the catalog.
This editing page contains the same information as Dr. Vandenbergs page containing faculty information within the Computer Science Department. The only difference this time is that the copy of the text on the right hand side contains editing done by both Dr. Vandenberg, and editing done by Ms. McKeever. Dr. Vandenbergs editing was done in red; Angela McKeevers edits were highlighted in blue font.
This editing page contains the same information as Dr. Vandenbergs page containing department information within the Computer Science Department. The only difference is that the copy of the text on the right hand side contains editing done by both Dr. Vandenberg, and editing done by Ms. McKeever. Dr. Vandenbergs editing was done in red; Angela McKeevers edits were highlighted in blue font.
College
Administrator Screens
The
home page for Vice Presidents (VP) of the college (as well as any college administrators
who may have access to the system) contains links for all of the sections of
the catalog that the given VP has access to, along with corresponding check
boxes. When the VP clicks on a section
of the catalog, the editing window will pop up and they will be able to make
the desired changes. When they are
finished editing the section they click the check box and click the Submit Changes button. When the Submit
Changes button is clicked it updates the files and status of their catalog
progress.
This is an example of a section of the catalog that Vice President of Enrollment and Planning Noel Hogan has the ability to access. As with all other editing windows, the left hand side contains the original text in the current catalog, while the right hand side has write permissions, allowing the user to edit the catalogs information.
This page also contains information that would require editing by Noel Hogan.
This page also contains information within the current catalog that would need to be edited by Noel Hogan.
This page also contains information that would need to be edited by Noel Hogan.
1.2: User Command Summary
Log
In (User Level 0, 1, 2)
The log in screen is the first screen that users will encounter. The log in screen contains two fields. The first field is for the users username, and the second field is for the users password. After the user enters their username and password into the respective fields they need to click the login button to continue. Upon clicking the login button the system verifies the username and password to make sure they are valid before taking the user to their next respective screen. If upon clicking the login button the system tries to verify the user data but cannot find a valid match an error message appears on the screen directing the user to re-enter a valid username and password and try again.
Academic
Affairs Home Page (User Level 0)
If the user data provided at the log in screen is for the Academic Affairs administrator the user is brought to the Academic Affairs home page. This page is the root page for the Academic Affairs administrator. The page contains links to the pages that allow the user to do various tasks, these links are: Create or Edit Users, Check User Progress, Edit Catalog, Generate Publishers Copy, View Current Catalog. When the user clicks on the Create or Edit Users link they are taken to a web page that displays links to other pages that allow the user to perform various tasks on users. When the user clicks the Check User Progress link they will be taken to a page that displays information relating to the progress of the other users of the system. The Edit Catalog link when clicked takes the user to a page where they have the options pertaining to the editing of different sections of the catalog. The Generate Publishers Copy link when clicked compiles all of the catalog data into a document that can be sent electronically to the publisher. The View Current Catalog link when clicked opens up a new window with the current version of the catalog displayed.
Create/Edit
User (User Level 0)
This page consists of links to the pages that allows the user to perform various tasks regarding the creation, editing, and deletion of users. The links are as follows: Create New User, Edit Existing User, Remove User. The Create New User link when clicked takes the user to a screen in which they are able to enter in the required information for new user creation. The Edit Existing User link when clicked brings the user to a screen that lists all the current users of the system. The Remove User link takes the user to a screen in which they have the ability to remove users from the system.
Create New User (User Level 0)
This page contains various fields for the following: User Name, User Password, User Email, User Title, User Office/Dept. There are also links to set permissions on various sections of the catalogs. To create a user, the administrative user enters information into the respective fields. The administrative user then clicks on the link for whatever category of the catalog permissions they wish to assign the new user. If the administrative user wishes to they can clear the form and start over if they wish to do so. After all new user information and permissions are set the administrative user can click the Create User button. Upon clicking the Create User button the new user will be created in the system with the entered information and password. If some information is missing a message saying so will appear.
Permissions (User Level 0)
The permission screens are broken down into sections depending on what part of the catalog they are under. In each permission screen the areas are broken down even further into specific subsections. To set the permissions the user selects by clicking in the corresponding check boxes. When all desired boxes are clicked then the Grant Permissions button is pressed and the users permissions are updated. If the user wants they can also clear all granted permissions by clicking the Clear Form button to unclick all checked permission boxes.
Edit User (User Level 0)
The edit user screen displays a listing of all users, along with titles and other information. From this page the administrative user can click on the desired persons name that they wish to modify. When they click on the page they are brought to a page called Edit User Info
Edit User Info (User Level 0)
The Edit User Info page is almost identical to the Create New User page. However, it is populated with the selected users information in all of the corresponding fields. Also, the selected users permissions are summarized so that the administrative user can easily tell what they have access to. From this screen the desired user can have any of their information and/or permissions modified.
Remove User (User Level 0)
This screen allows for the administrative user to delete any user. To delete a user the administrative user selects the desired user from the list of all users. After the desired user is selected they the Remove User button is pushed and the user is deleted from the program.
User Progress (User Level 0)
The User Progress screen displays the same information as the edit user screen. In addition this screen contains a summary of which users have completed their portion of the catalog. The administrative user can then click on a users name and a message will automatically be generated and sent to the user corresponding user reminding them to complete their portion of the catalog.
Review/Edit Changes (User Level 0)
The Review/Edit Changes screen allows the administrative user to select a user from a list of all users. The administrative user is then redirected to another screen pertaining to the actual editing of sections.
Review/Edit User Name Changes (User Level 0)
The Review/Edit User Name Changes allows the administrative user to click on the section of the catalog they wish to review for the previously selected user. Upon clicking on the section of the catalog the sections pop up for editing. When the administrative user finished making changes they click in the complete box and click submit changes to update the file.
Assistant Dean Home Page (User Level 1)
The Assistant Dean Home Page is the page that an Assistant Dean is taken to when they log in at the Log In screen. It contains links to all of the different that the Assistant Dean needs to change or monitor. The links include the following: Edit Given School General Information, Review Progress, and Review/Edit Changes. The Edit Given School General Information link when clicked opens the general information section of the given school for editing. When editing is completed the appropriate check box should be checked to indicate that the user is finished editing that section. The View Progress link takes the user to a system of pages and functionality much like the View Progress link for the User Level 0. However, the Assistant Dean can only view the progress of the Department Heads in their school. The Review/Edit Changes link is much like the series of Review/Edit Changes pages that the User Level 0 has. However, the Assistant Dean can only review and/or edit changes for the Department Heads in their school.
Vice President Home Page (User Level 1)
The Vice President Home Page contains links for all of the sections of the catalog that the given VP has access to along with corresponding check boxes. When the VP clicks on a section of the catalog the editing window will pop up and they will be able to make the desired changes. When they are finished editing the section they click the check box and click the Submit Changes button. When the Submit Changes button is clicked it updates the files and status of their catalog progress.
Department Head Home Page (User Level 2)
The Department Head Home Page contains links for all of the sections of the catalog that the given Department Head has access to change, along with corresponding check boxes, and a link to view the course descriptions in their given department. The Department Head clicks on his/her given link for the section of catalog they wish to edit and an editing window pops up. When they are finished editing the section they click the check box and click the Submit Changes button to submit their changes and update their catalog progress. When the View Course Description is clicked the Department Head will be able to view the course descriptions that are in their department in a read only manner.
1.3: Detailed Data Flow Diagrams
1.4:
Logical Data Dictionary
The following information describes the data elements within the data flow diagrams (located in section 1.3 Detailed Data Flow Diagrams). The data elements are separated by the location (i.e., which data flow diagram) they are located within.
Location
Context Diagram:
Description:
In actuality, signifies the head user/system
administrator (i.e. Ms. Zimmerman), who has complete control
Input Flows:
Proofs
Updated-DB-to-Academic-Affairs
Output Flows:
Approval
Final-changes
Final-Approval
Academic-Affairs-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Academic Affairs can make any changes to the
catalog.
Source: Academic Affairs ( Source/Sink )
Dest: College Catalog Software ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Administrator changes are made to any necessary
sections of the catalog that are not included in the academic portions
Source: College Administrator ( Source/Sink )
Dest: College Catalog Software ( Process )
Date Last Altered:
Description:
Final approval of the College Catalog to be printed.
Source: Academic Affairs ( Source/Sink )
Dest: Publisher ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Anyone at the Dean level of the college; has the
ability to access the database, make changes, and monitor
Input Flows:
Updated-DB-to-Asst.-Dean
Output Flows:
Dean-Approval
Dean-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Data store; Database used by
Output Flows:
Course-Information
Faculty-Listings
-------------------------------------------------------------------------------------------------------------------------------
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Input Flows:
Course-Information
Faculty-Listings
User-Updates
Output Flows:
Final-Information
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to administrative policies in areas
not included in the schools.
Input Flows:
Updated-DB-to-Admin
Output Flows:
Admin-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Allows for editing of the college catalog
Input Flows:
Final-Approval
Dean-Approval
Dean-Changes
Academic-Affairs-Changes
Department-Changes
Admin-Changes
Final-Information
Output Flows:
Updated-DB-to-Academic-Affairs
Updated-DB-to-Asst.-Dean
Updated-DB-to-Dept.
Updated-DB-to-Admin
Web-Catalog
User-Updates
-------------------------------------------------------------------------------------------------------------------------------
Course-Information Data Flow
Description:
Contains course information.
Source: Banner ( File )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Dean must approve changes made to the
departments within its school.
Source: Assistant Dean ( Source/Sink )
Dest: College Catalog Software ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Dean can make any changes to any of the
departments within its particular school.
Source: Assistant Dean ( Source/Sink )
Dest: College Catalog Software ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to the particular scholastic
department
Input Flows:
Updated-DB-to-Dept.
Output Flows:
Department-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Department heads make changes to only their specific
department.
Source: Department Head ( Source/Sink )
Dest: College Catalog Software ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Faculty information
Source: Banner ( File )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Academic Affairs has the final approval on all
changes to be made to the catalog.
Source: Academic Affairs ( Source/Sink )
Dest: College Catalog Software ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Academic Affairs Office sends any final changes
it needs to make to the catalog.
Source: Academic Affairs ( Source/Sink )
Dest: Publisher ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
This information is any information sent from the
database back into the College Catalog Software.
Source: Catalog DB ( File )
Dest: College Catalog Software ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Proofs are the drafts of the catalog that are sent
back for approval.
Source: Publisher ( Source/Sink )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Outside publishing editor; puts together the hard
copy of the final college catalog
Input Flows:
Approval
Final-changes
Output Flows:
Proofs
-------------------------------------------------------------------------------------------------------------------------------
Description:
Anyone with access to the catalog; access limited to
read-only privileges (can read the catalog)
Input Flows:
Web-Catalog
-------------------------------------------------------------------------------------------------------------------------------
Description:
Academic Affairs is notified of any changes made to
the College Catalog database.
Source: College Catalog Software ( Process )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The College Administrators can see any changes made
by anyone else to their sections.
Source: College Catalog Software ( Process )
Dest: College Administrator ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Dean will be notified whenever changes are made
to any departments within the particular school.
Source: College Catalog Software ( Process )
Dest: Assistant Dean ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Department Heads can see any changes made by anyone
else to their sections.
Source: College Catalog Software ( Process )
Dest: Department Head ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Any updates made to the catalog database.
Source: College Catalog Software ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Web Catalog is available to all users.
Source: College Catalog Software ( Process )
Dest: Universal User ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Location
Level 0 Diagram:
Description:
In actuality, signifies the head user/system
administrator (i.e. Ms. Zimmerman), who has complete control
Input Flows:
Final-Approval-Request
All-Catalog-Changes
Published-Proofs
Output Flows:
Academic-Affairs-Approval
Academic-Affairs-Changes
Proof-Approval
Final-Catalog-Changes
Proof-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Academic Affairs makes all final approvals.
Source: Academic Affairs ( Source/Sink )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Academic Affairs can make any changes to the catalog.
Source: Academic Affairs ( Source/Sink )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Source: College Administrator ( Source/Sink )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Academic Affairs is notified of any Catalog changes.
Source: Coordinate Web Process ( Process )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Requests that changes be approved.
Source: Manage Data ( Process )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Anyone at the Dean level of the college; has the
ability to access the database, make changes, and monitor
Input Flows:
Updated-DB-to-Asst.-Dean
Output Flows:
Dean-Changes
Dean-Approval
Dean-Approval
-------------------------------------------------------------------------------------------------------------------------------
Description:
Data store; Database used by
Output Flows:
Course-Information
Faculty-Listings
-------------------------------------------------------------------------------------------------------------------------------
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Input Flows:
Course-Information
Faculty-Listings
Output Flows:
Data
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to administrative policies in areas
not included in the schools.
Input Flows:
Updated-DB-to-Admin
Output Flows:
Administrator-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Coordinates changes made to the database via the
internet; allows for authorized users to login to a user-fr
Input Flows:
Dean-Changes
Dean-Approval
Department-Changes
Administrator-Changes
Academic-Affairs-Approval
Academic-Affairs-Changes
Updated-Query-Results
Approval-Request
Dean-Approval
Output Flows:
Final-Approval-Request
All-Catalog-Changes
Update-Query
Updated-DB-to-Asst.-Dean
Updated-DB-to-Dept.
Updated-DB-to-Admin
-------------------------------------------------------------------------------------------------------------------------------
Description:
Contains course information.
Source: Banner ( File )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Contains any data coming from the College Catalog
DB.
Source: Catalog DB ( File )
Dest: Manage Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Dean must approve changes made to the departments
within its school.
Source: Assistant Dean ( Source/Sink )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Dean can make any changes to any of the
departments within its particular school.
Source: Assistant Dean ( Source/Sink )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to the particular scholastic
department
Input Flows:
Updated-DB-to-Dept.
Output Flows:
Department-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Department heads make changes to only their specific
department.
Source: Department Head ( Source/Sink )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Faculty information
Source: Banner ( File )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
All users must submit their changes for final
approval.
Source: Coordinate Web Process ( Process )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
All final Catalog changes are sent to the publisher.
Source: Academic Affairs ( Source/Sink )
Dest: Publisher ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Process to manage the data submitted through the web
interface based on authorization and approval
Input Flows:
Update-Query
Data
Output Flows:
Updated-Query-Results
Approval-Request
-------------------------------------------------------------------------------------------------------------------------------
Description:
The proofs are approved and are ready to be printed.
Source: Academic Affairs ( Source/Sink )
Dest: Publisher ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Academic Affairs sends any changes to the proofs.
Source: Academic Affairs ( Source/Sink )
Dest: Publisher ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The published proofs are sent back for approval.
Source: Publisher ( Source/Sink )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Outside publishing editor; puts together the hard copy
of the final college catalog
Input Flows:
Proof-Approval
Final-Catalog-Changes
Proof-Changes
Output Flows:
Published-Proofs
-------------------------------------------------------------------------------------------------------------------------------
Description:
The College Administrators can see any changes made
by anyone else to their sections.
Source: Coordinate Web Process ( Process )
Dest: College Administrator ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Dean will be notified whenever changes are made
to any departments within the particular school.
Source: Coordinate Web Process ( Process )
Dest: Assistant Dean ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Department Heads can see any changes made by anyone
else to their sections.
Source: Coordinate Web Process ( Process )
Dest: Department Head ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Submits any update queries that are approved to the
catalog database.
Source: Manage Data ( Process )
Dest: Coordinate Web Process ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Submission for changes to be made to the Catalog
database.
Source: Coordinate Web Process ( Process )
Dest: Manage Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Location
Level 1 Diagram Coordinate Web Processes:
Description:
Access respective to the user rights of the Academic
Affairs head user are granted, pending authetication o
Source: Authenticate ( Process )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Academic Affairs head user (i.e., Ms. Zimmerman)
must approve all final changes to the catalog data
Source: Academic Affairs ( Source/Sink )
Dest: Change Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The head user from the Academic Affairs office
(i.e., Ms. Zimmerman) submits a user ID and password to
Source: Academic Affairs ( Source/Sink )
Dest: Authenticate ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Academic Affairs head user (i.e., Ms. Zimmerman)
has the ability to submit information to be update
Source: Academic Affairs ( Source/Sink )
Dest: Change Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
In actuality, signifies the head user/system
administrator (i.e. Ms. Zimmerman), who has complete control
Input Flows:
AA-Access-Granted
Output Flows:
AA-ID-and-Password
AA-update-Query
AA-Final-Approval
-------------------------------------------------------------------------------------------------------------------------------
Description:
Access respective to the user rights of a College
Administrator are granted, pending authetication of the u
Source: Authenticate ( Process )
Dest: College Administrator ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
A College Administrator submits a user ID and
password to the system for authetication
Source: College Administrator ( Source/Sink )
Dest: Authenticate ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
A College Administrator has the ability to submit
information to be updated within the database.
Source: College Administrator ( Source/Sink )
Dest: Change Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Anyone at the Dean level of the college; has the
ability to access the database, make changes, and monitor
Input Flows:
Dean-Access-Granted
Output Flows:
Dean-ID-and-Password
Dean-Update-Query
Dean-Approval
-------------------------------------------------------------------------------------------------------------------------------
Description:
Verify username and password at login as valid,
authorized user
Input Flows:
Dean-ID-and-Password
Department-ID-and-Password
Admin-ID-and-Password
AA-ID-and-Password
Selected-Query-Results
Output Flows:
Dean-Access-Granted
Department-Access-Granted
Admin-Access-Granted
AA-Access-Granted
Information-Query
-------------------------------------------------------------------------------------------------------------------------------
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Input Flows:
Information-Query
Updated-Query-Results
New-Catalog-Entry
Output Flows:
Selected-Query-Results
-------------------------------------------------------------------------------------------------------------------------------
Change Data Process
Description:
The process to submit changes to the current data in
the catalog database
Input Flows:
AA-update-Query
AA-Final-Approval
Administrator-Update-Query
Department-Head-Update-Query
Dean-Update-Query
Dean-Approval
Output Flows:
Updated-Query-Results
New-Catalog-Entry
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to administrative policies in areas
not included in the schools.
Input Flows:
Admin-Access-Granted
Output Flows:
Admin-ID-and-Password
Administrator-Update-Query
-------------------------------------------------------------------------------------------------------------------------------
Description:
Access respective to the user rights of the
Assistant Dean are granted, pending authetication of the user ID
Source: Authenticate ( Process )
Dest: Assistant Dean ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Dean must approve changes made to the
departments within its school.
Source: Assistant Dean ( Source/Sink )
Dest: Change Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Assistant Dean submits a user ID and password to
the system for authetication
Source: Assistant Dean ( Source/Sink )
Dest: Authenticate ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Assistant Dean has the ability to submit
information to be updated within the database.
Source: Assistant Dean ( Source/Sink )
Dest: Change Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Department Head Source/Sink
Description:
Makes changes to the particular scholastic
department
Input Flows:
Department-Access-Granted
Output Flows:
Department-ID-and-Password
Department-Head-Update-Query
-------------------------------------------------------------------------------------------------------------------------------
Description:
Access respective to the user rights of the
Department Head are granted, pending authetication of the user
Source: Authenticate ( Process )
Dest: Department Head ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Department Head has the ability to submit
information to be updated within the database.
Source: Department Head ( Source/Sink )
Dest: Change Data ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Department Head submits a user ID and password
to the system for authetication
Source: Department Head ( Source/Sink )
Dest: Authenticate ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Checks with catalog database to make sure user IDs
and passwords are saved in the system.
Source: Authenticate ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Enters any new catalog entries that were added by
any authorized users with the ability to update into the
Source: Change Data ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Privileges of a particular user (based on the user
ID and password submited in the information query) are
Source: Catalog DB ( File )
Dest: Authenticate ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Submits any update queries that are approved to the
catalog database.
Source: Change Data ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Location Authenticate:
Description:
The head user from the Academic Affairs office
(i.e., Ms. Zimmerman) submits a user ID and password to
Source: Academic Affairs ( Source/Sink )
Dest: Login Authentication ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
In actuality, signifies the head user/system
administrator (i.e. Ms. Zimmerman), who has complete control
Input Flows:
Access-to-All-Forms
Output Flows:
AA-ID-and-Password
-------------------------------------------------------------------------------------------------------------------------------
Description:
Access to all catalog content is granted
Source: Catalog DB ( File )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Access to all content for a particular school is
granted
Source: Catalog DB ( File )
Dest: Assistant Dean ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Access to individual departments given to Department
Heads
Source: Catalog DB ( File )
Dest: Department Head ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
A College Administrator submits a user ID and
password to the system for authetication
Source: College Administrator ( Source/Sink )
Dest: Login Authentication ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Administrator-Access Data Flow
Description:
College administrator access is granted to their
particular office(s).
Source: Catalog DB ( File )
Dest: College Administrator ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Anyone at the Dean level of the college; has the
ability to access the database, make changes, and monitor
Input Flows:
Access-to-All-Forms-within-School
Output Flows:
Dean-ID-and-Password
-------------------------------------------------------------------------------------------------------------------------------
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Input Flows:
User-Access-Level-Selection
Output Flows:
Access-to-All-Forms
Access-to-All-Forms-within-School
Access-to-Own-Department-Forms
Administrator-Access
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to administrative policies in areas
not included in the schools.
Input Flows:
Administrator-Access
Output Flows:
Admin-ID-and-Password
-------------------------------------------------------------------------------------------------------------------------------
Description:
The Assistant Dean submits a user ID and password to
the system for authetication
Source: Assistant Dean ( Source/Sink )
Dest: Login Authentication ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to the particular scholastic
department
Input Flows:
Access-to-Own-Department-Forms
Output Flows:
Department-Head-ID-and-Password
-------------------------------------------------------------------------------------------------------------------------------
Department-Head-ID-and-Password Data Flow
Description:
Department Heads ID and Password are sent to be
authenticated
Source: Department Head ( Source/Sink )
Dest: Login Authentication ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Takes user ID and password and verifies user
authority to access the catalog database
Input Flows:
AA-ID-and-Password
Dean-ID-and-Password
Department-Head-ID-and-Password
Admin-ID-and-Password
Output Flows:
User-Access-Level-Selection
-------------------------------------------------------------------------------------------------------------------------------
Description:
Access level requested from database
Source: Login Authentication ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Location
Change Data:
Description:
In actuality, signifies the head user/system
administrator (i.e. Ms. Zimmerman), who has complete control
Input Flows:
Changes
Output Flows:
All-Final-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Assistant Dean submits changes for their particular
school.
Source: Assistant Dean ( Source/Sink )
Dest: Submits For Academic Affairs Approval ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
All changes to any part of the catalog are submitted
to the catalog database to update the records.
Source: Academic Affairs ( Source/Sink )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Assistant Dean Source/Sink
Description:
Anyone at the Dean level of the college; has the
ability to access the database, make changes, and monitor
Input Flows:
Department-Changes
Output Flows:
All-Approved-Department-Changes
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Input Flows:
All-Final-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
All changes from all departments, schools, and
offices of the college are submitted for Academic Affairs a
Source: Submits For Academic Affairs Approval ( Process )
Dest: Academic Affairs ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to administrative policies in areas
not included in the schools.
Output Flows:
Pertinent-Administrative-Policy
-------------------------------------------------------------------------------------------------------------------------------
Description:
Verifies that the course information in Banner is
correct.
Source: Department Head ( Source/Sink )
Dest: Submit For Dean Approval ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Makes changes to the particular scholastic
department
Output Flows:
Faculty-Info-Check
Department-Info-Changes
Course-Info-Check
-------------------------------------------------------------------------------------------------------------------------------
Description:
Department heads make changes to only their specific
department.
Source: Submit For Dean Approval ( Process )
Dest: Assistant Dean ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Department-Info-Changes Data Flow
Description:
Submit any changes to the department information.
Source: Department Head ( Source/Sink )
Dest: Submit For Dean Approval ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Verifies that the faculty information in Banner is
correct.
Source: Department Head ( Source/Sink )
Dest: Submit For Dean Approval ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Submit any college policy changes.
Source: College Administrator ( Source/Sink )
Dest: Submits For Academic Affairs Approval ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Process to send approval request to user at Dean
level
Input Flows:
Faculty-Info-Check
Department-Info-Changes
Course-Info-Check
Output Flows:
Department-Changes
-------------------------------------------------------------------------------------------------------------------------------
Description:
Submit request for final approval on all changes
from Academic Affairs
Input Flows:
All-Approved-Department-Changes
Pertinent-Administrative-Policy
Output Flows:
Changes
-------------------------------------------------------------------------------------------------------------------------------
Location
Level 1 Diagram Manage Data:
Description:
In actuality, signifies the head user/system
administrator (i.e. Ms. Zimmerman), who has complete control
Output Flows:
Database-Composition-Prompt
-------------------------------------------------------------------------------------------------------------------------------
Banner File
Description:
Data store; Database used by
Input Flows:
Banner-Information-Request
Output Flows:
Faculty-Info
Course-Info
-------------------------------------------------------------------------------------------------------------------------------
Description:
Process to format Banner information from Banner
tables and append them to the Catalog DB tables
Input Flows:
Database-Composition-Prompt
Faculty-Info
Course-Info
Output Flows:
Banner-Information-Request
Banner-Info
-------------------------------------------------------------------------------------------------------------------------------
Description:
Updated Banner information submitted to catalog
database for storage.
Source: Banner Import ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Banner requested to update faculty and course
information, to prepare for submission to the catalog databa
Source: Banner Import ( Process )
Dest: Banner ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Input Flows:
Banner-Info
Catalog-DB-Information-Request
Output Flows:
Catalog-DB-Information-Return
-------------------------------------------------------------------------------------------------------------------------------
Description:
User requests information from the database.
Source: Query Handler ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Catalog-DB-Information-Return Data Flow
Description:
Catalog database returns the information requested
in the catalog-DB-information-query.
Source: Catalog DB ( File )
Dest: Query Handler ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Course-Info Data Flow
Description:
Contains information about courses.
Source: Banner ( File )
Dest: Banner Import ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Query to prompt for updated faculty and course
information from Banner
Source: Academic Affairs ( Source/Sink )
Dest: Banner Import ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Contains faculty information to be added to the
database from Banner.
Source: Banner ( File )
Dest: Banner Import ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Allows user to request information from the Catalog
DB and sends information back to said user
Input Flows:
Catalog-DB-Information-Return
Output Flows:
Catalog-DB-Information-Request
-------------------------------------------------------------------------------------------------------------------------------
Location
Query Handler:
Description:
Any user with the ability to make changes to the
catalog
Input Flows:
Query-Results
Output Flows:
Query-Submission
Updated-Query
-------------------------------------------------------------------------------------------------------------------------------
Catalog DB File
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Input Flows:
Database-Information
Output Flows:
Data
-------------------------------------------------------------------------------------------------------------------------------
Description:
Contains any data coming from the College Catalog
DB.
Source: Catalog DB ( File )
Dest: Format Results ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
All database information submitted for the catalog.
Source: Query ( Process )
Dest: Catalog DB ( File )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Format queried results into aesthetically pleasing,
easy to read text and possibly graphics
Input Flows:
Data
Output Flows:
Query-Results
-------------------------------------------------------------------------------------------------------------------------------
Description:
Request information from Catalog DB
Input Flows:
Query-Submission
Updated-Query
Output Flows:
Database-Information
-------------------------------------------------------------------------------------------------------------------------------
Description:
Formatted data returned to any user.
Source: Format Results ( Process )
Dest: All Users ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Submit new information to the catalog
Source: All Users ( Source/Sink )
Dest: Query ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Update information that already exists in the
catalog.
Source: All Users ( Source/Sink )
Dest: Query ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Location
Format Results:
Description:
Any user with the ability to make changes to the
catalog
Input Flows:
Query-Results
-------------------------------------------------------------------------------------------------------------------------------
Description:
Database containing all the College catalog
information (different from Banner catalog database)
Output Flows:
Data
-------------------------------------------------------------------------------------------------------------------------------
Description:
Converts parced text to an HTML format so that is is
viewable to the users.
Input Flows:
Parced-Text
Output Flows:
Query-Results
-------------------------------------------------------------------------------------------------------------------------------
Description:
Converts any raw data to parced text.
Input Flows:
Data
Output Flows:
Parced-Text
-------------------------------------------------------------------------------------------------------------------------------
Description:
Contains any data coming from the College Catalog
DB.
Source: Catalog DB ( File )
Dest: Convert to Parsed Text ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Parced Text.
Source: Convert to Parsed Text ( Process )
Dest: Convert to HTML Format ( Process )
-------------------------------------------------------------------------------------------------------------------------------
Description:
Formatted data returned to any user.
Source: Convert to HTML Format ( Process )
Dest: All Users ( Source/Sink )
-------------------------------------------------------------------------------------------------------------------------------
1.5:
Logical Data Stores
After consulting with our clients, Ms. Zimmerman and Mr. Smith, our group, in collaboration with IniTech software engineering group, compiled a list of all sections and subsections of the college catalog (as it was prepared for the 2004-2005 academic year). Along with this information, we indicated who would be editing this information, and the chain of command in which any given section will be edited and/or approved.
The following is that compiled list:
Table
of Contents:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Kate Zimmerman (or appointee)
Hierarchy: None
Communications
Directory:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Kate Zimmerman (or appointee)
Hierarchy: None
Academic
Calendar:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Kate Zimmerman (or appointee)
Hierarchy: None
Source: Text file
General
Information
College VP Area: President of the College
Editor: Fr. Kevin Mackin, O.F.M. (or appointee)
Hierarchy: President ΰ Kate Zimmerman
Founding
of the College
College VP Area: President of the College
Editor: Fr. Kevin Mackin, O.F.M. (or appointee)
Hierarchy: President ΰ Kate Zimmerman
College VP Area: President of the College
Editor: Fr. Kevin Mackin, O.F.M. (or appointee)
Hierarchy: President ΰ
Kate Zimmerman
College VP Area: President of the College
Editor: Fr. Kevin Mackin, O.F.M. (or appointee)
Hierarchy: President ΰ Kate Zimmerman
Accreditation
College VP Area: Vice President for Enrollment and Planning
Editor: Noel Hogan (or appointee)
Hierarchy: VPEP ΰ Kate Zimmerman
Retention
Rates
College VP Area: Vice President for Enrollment and Planning
Editor: Noel Hogan (or appointee)
Hierarchy: VPEP ΰ Kate Zimmerman
Growth of Campus Facilities
College VP Area: Vice President, Office of the President
Editor: Fr. James Toal, O.F.M. (or appointee)
Hierarchy: VPOP ΰ Kate Zimmerman
Library
/ Audiovisual Resources
College VP Area: Vice President of Academic Affairs
Editor: Linda Richardson (or appointee)
Hierarchy: VPAA ΰ Kate Zimmerman
Information & Technology Services
College VP Area: Vice President of Finance & Administration
Editor: Paul Stec (or appointee)
Hierarchy: VPFA ΰ Kate Zimmerman
Computer
Ethics
College VP Area: Vice President of Finance & Administration
Editor: Paul Stec (or appointee)
Hierarchy: VPFA ΰ Kate Zimmerman
Academic
Integrity
College VP Area: Vice President of Academic Affairs
Editor: Linda Richardson (or appointee)
Hierarchy: VPAA ΰ Kate Zimmerman
Student
Records -Family Education Rights &
College VP Area: Vice President of Academic Affairs
Editor: Linda Richardson (or appointee)
Hierarchy: VPAA ΰ Kate Zimmerman
Student
Access to Records
College VP Area: Vice President of Academic Affairs
Editor: Linda Richardson (or appointee)
Hierarchy: VPAA ΰ Kate Zimmerman
College VP Area: Vice President of Student Affairs
Editor: Maryellen Gilroy (or appointee)
Hierarchy: VPSA ΰ Kate Zimmerman
Campus
Crime Statistics
College VP Area: Vice President, Office of the President
Editor: Fr. James Toal, O.F.M. (or appointee)
Hierarchy: VPOP ΰ Kate Zimmerman
Compliance
Statements
College VP Area: Vice President of Finance & Administration
Editor: Paul Stec (or appointee)
Hierarchy: VPFA ΰ Kate Zimmerman
Changes
in College Regulations
College VP Area: Vice President of Finance & Administration
Editor: Paul Stec (or appointee)
Hierarchy: VPFA ΰ Kate Zimmerman
Admission
to the College:
Source: Text file
College VP Area: Vice President of Enrollment & Planning
Editor: Noel Hogan (or appointee)
Hierarchy: VPEP ΰ Kate Zimmerman
Interviews
High School Course Requirements
When & How to Apply
Early Admission
Early Decision
Early Action
Higher Education
International Applicants
Transfer Students
Re-entry Students
Non-matriculated Students
Auditing Students
International Students
Advanced Placement
International Baccalaureate
Undergraduate
Tuition & Fees:
Source: Text file
College VP Area: Vice President of Finance & Administration
Editor: Paul Stec (or appointee)
Hierarchy: VPFA ΰ Kate Zimmerman
Procedure for Payment
Payment by Check
Deposit
Rooms & Meals
Books & Supplies
General Estimate of Cost
Withdrawals & Refunds
Room & Board Fees
Academic
Info & Regulations:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Linda Richardson (or appointee)
Hierarchy: VPAA ΰ Kate Zimmerman
Degree
Requirements:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Linda Richardson (or appointee)
Hierarchy: VPAA ΰ Kate Zimmerman
The following are the subsections for this section:
Major
Changing Schools
Change of Major
Minor
Double Majors
Double Degrees - Simultaneous Awarding
Second Degree
Transfer Credit for Matriculated
Graduation
Regular &
Summer Sessions
Day &
Evening Sessions
Unit of
Instruction
Absences from
Class
Change of
Address
Pass/Fail
Option
Adding a Course
Dropping a
Course
Examinations
College
Proficiency Examinations, Noncoll
Academic
Classification
System of
Grading
Grade Reports
Appeal of
Assigned Grades
Scholarship
Indices (G.P.A)
Repeated
Courses
Transcript of
Record
Honor Lists
Honor Society
Graduation
Honors
Good Academic
Standing
Academic
Probation & Academic Dismissal
Withdrawing
from the College
Separation from
the College
Snow Day
Procedure
Faculty
Attendance Policies
Courses
of Instruction:
Source: Banner
College VP Area: Vice President of Academic Affairs
Editor: Linda Richardson (or appointee)
Hierarchy: VPAA ΰ Kate Zimmerman
Multidisciplinary
Courses, Certificates, etc.:
College VP Area: Vice President of Academic Affairs
Editor: Program Director
Hierarchy: Program Director ΰ Kate Zimmerman
Convivium
Source: Text file
Course
Desc
Source: Banner
Criminal
Justice Minor Environmental Studies Certificate Program
General
Info
Source: Text file
Foundations
Sequence
General
Info
Source: Text file
Source: Banner
Franciscan
Service & Advocacy Minor
General
Info
Source: Text file
Course
List/Requirements
Source: Banner
Course
Desc
Source: Banner
Globalization
Studies Minor
Professors
Source: Text file
General
Info
Source: Text file
Course
List/Requirements
Source: Banner
Course
Desc
Source: Banner
Health
Care Minors
General
Info
Source: Text file
Course
List/Requirements
Source: Banner
Honors
Program
General
Info
Source: Text file
International
Studies:
College VP Area: Vice President of Academic Affairs
Editor: Program Director
Hierarchy: Program Director ΰ Kate Zimmerman
Foreign
Language & Business Cert Program
Source: Text file
General
Info
Source: Text file
Course
List/Requirements
Source: Banner
Multicultural
Studies Minor
Source: Text file
Course
List/Requirements
Source: Banner
Course
Desc
Source: Banner
Peace
Studies Certificate Program
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Women's
Studies Minor
Source: Text file
Course
List/Requirements
Source: Banner
Course
Desc
Source: Banner
College VP Area: Vice President of Academic Affairs
Hierarchy: Department Head/Program Director ΰ Assistant Dean ΰ Kate Zimmerman
Source: Text file
Editor: Assistant Dean (or appointee)
Course
Desc
Source: Banner
Editor: Assistant Dean (or appointee)
American Studies Program
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Creative
Arts
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Theatre
Program
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Education
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
English
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
English
Honors Program
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
History
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
History
Honors Program
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Modern
Language & Classics Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
American
Sign Language
Course
Desc
Source: Banner
French
Course
Desc
Source: Banner
German
Course
Desc
Source: Banner
Russian
Course
Desc
Source: Banner
Spanish
Course
Desc
Source: Banner
Classics
Latin
Course
Desc
Source: Banner
Greek
Course
Desc
Source: Banner
Greek
Classical Studies
Course
Desc
Source: Banner
Philosophy
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Political
Science Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Psychology
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Religious
Studies Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Social
Work Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Sociology
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
College VP Area: Vice President of Academic Affairs
Hierarchy: Department Head/Program Director ΰ Assistant Dean ΰ Kate Zimmerman
Accounting
and Business Law
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Business
Law
Course
Desc
Source: Banner
Economics
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Finance
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Marketing
Management Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Quantitative
Business Analysis Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
College VP Area: Vice President of Academic Affairs
Hierarchy: Department Head/Program Director ΰ Assistant Dean ΰ Kate Zimmerman
Biology
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Chemistry
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Computer
Science Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Environmental
Studies Program
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Mathematics
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Physics
Dept
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Military
Science Department:
College VP Area: Vice President of Academic Affairs
Editor: Department Head
Hierarchy: Department Head ΰ
Kate Zimmerman
Source: Text file
General
Info
Source: Text file
Course
Desc
Source: Banner
Off
Campus Opportunities:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Program Director
Hierarchy: Program Director ΰ Kate Zimmerman
Study Abroad General Info
Pre-Professional
Studies:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Program Director(s)
Hierarchy: Program Director(s) ΰ Kate Zimmerman
The following are the subsections for this section:
Pre-Medical, Pre-Dental and other Health-Related Studies
General Info
Allied Health Professions General Info
Affiliation/Articulation Agreements:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Program Director(s)
Hierarchy: Program Director ΰ Kate Zimmerman
The following are the subsections for this section:
2-
Year Institutions General Info
Business
Management Programs General Info
Engineering
Programs General Info
Environmental
Science/ Forestry Program General Info
Hudson-Mohawk
Association General Info
Social
Work Masters Program General Info
SUNY
Special Programs:
Source: Text file
College VP Area: Vice President, Office of the President
Editor: Fr. James Toal, O.F.M. (or appointee)
Hierarchy: VPOP ΰ Kate Zimmerman
The following are the subsections for this section:
Kieval
Institute for Jewish Christian Studies General Info
MLK
Jr. and Coretta Scott King Lecture Series on Race and Nonviolent Social Change
General Info
Reinhold
Niebuhr Institure of Religion and Culture General Info
Siena
Business Institute General Info
Siena
Research Institute General Info
The
Source: Text file
College VP Area: Vice President, Office of the President
Editor: Maryellen Gilroy (or appointee)
Hierarchy: VPSA ΰ Kate Zimmerman
The following are the subsections for this section:
Office of College Chaplain General Info
Student Life General Info
Student Government General Info
Student Activities General Info
Weekend Activities General Info
Athletics Program General Info
Concerts General Info
Guest Lecturers General Info
Residence Life General Info
Motor Vehicle Registration and Traffic
Violations General Info
Dining General Info
Student Services Orientation General Info
Commuter Students General Info
Sarazen Student Union General Info
Multicultural Affairs General Info
The
Office of Tutoring and Services for
Students with Disabilities General Info
Learning Support Services General Info
Health Services General Info
Career
Services:
Source: Text document
College VP Area: Vice President of Academic Affairs
Editor: Thomas Denham, Director of
the
Hierarchy: Director of
Financial
Aid:
Source: Text file
College VP Area: Vice President for Enrollment Planning
Editor: Noel Hogan (or appointee)
Hierarchy: VPEP ΰ Kate Zimmerman
The following are the subsections for this section:
General Info
Grants and Scholarships General Info
State and Federal Aid Programs General
Info
Criteria for Renewal of Financial Aid
General Info
Satisfactory Academic Progress General
Info
Federal Aid General Info
NYS Aid General Info
Appealing the Withdrawal of Aid General
Info
State and Federal Aid Programs Descriptions
Directory:
Source: Banner
Hierarchy: Kate Zimmerman
The following are the subsections for this section:
Board of Trustees
Office of the President
Office of the Vice President
Athletic Department
Office of the College Chaplain
Plant Operations
Safety and Security
Office of VP for Academic Affairs
School Officers
HEOP
Library/Audio Visual Services
Center for Continuing and Professional
Education
Office of International Programs
Office of the Registrar
Office of Tutoring and Services for
Students with Disabilities
Office of the VP for Community and Public
Affairs
WVCR
Office of VP for Enrollment and Planning
Office of Admissions
Office of Financial Aid
Communications
Office of Enrollment and Planning
Office of the VP for Finance and
Administation
Business Affairs
Human Resources
Information & Technology Services
Post Office
Purchasing
Office of VP for Institutional
Advancement
Alumni Relations
Annual Fund
Office of the VP for Student Affairs
Health Services
Residence Life
Campus Programs
Multicultural Affairs
Full-Time Faculty
Part-Time Faculty
Professors Emeriti
Vice President Emeritus
Registrar Emerita
The final subsection does not follow the same format, and is as follows:
Source: Text file
College VP Area: Vice President of Academic Affairs
Editor: Kate Zimmerman
Hierarchy: None
Index:
Source: Text File
Editor: Publisher
Hierarchy: Publisher ΰ
Kate Zimmerman
Directions to the College:
Source: Text document
College VP Area: Vice President, Office of the President
Editor: Fr. James Toal, O.F.M. (or appointee)
Hierarchy: VPOP ΰ Kate Zimmerman
Additionally, our group, in a collaborative effort with IniTech, we met with Jim Serbalik, Director of the Registrar, and Stephanie Kot, a staff member in Information & Technology Services (I&TS). Mr. Serbalik and Ms. Kot informed us of the forms and the tables (associated with the forms) that we would need access to from Banner to gather information for our database.
The following are a list of the tables and fields necessary for our database, organized by the forms we would need access to from Banner:
Form:
SCARRES (owned by Registrar)
Fields: SCRRCOL_SUBJ_CODE
SCRRCOL_CRSE_NUMB
SCRRCOL_EFF_TERM
SCRRCOL_REC_TYPE
SCRRCOL_COLL_IND
SCRRCOL_COLL_CODE
SCRRCOL_ACTIVITY_DATE
Fields: SCRRMAJ_SUBJ_CODE
SCRRMAJ_CRSE_NUMB
SCRRMAJ_EFF_TERM
SCRRMAJ_REC_TYPE
SCRRMAJ_MAJOR_IND
SCRRMAJ_MAJR_CODE
SCRRMAJ_ACTIVITY_DATE
Fields: SCRRCLS_SUBJ_CODE
SCRRCLS_CRSE_NUMB
SCRRCLS_EFF_TERM
SCRRCLS_REC_TYPE
SCRRCLS_CLASS_IND
SCRRCLS_CLAS_CODE
SCRRCLS_ACTIVITY_DATE
Fields: SCRRLVL_SUBJ_CODE
SCRRLVL_CRSE_NUMB
SCRRLVL_EFF_TERM
SCRRLVL_REC_TYPE
SCRRLVL_LEVL_IND
SCRRLVL_LEVL_CODE
SCRRLVL_ACTIVITY_DATE
Fields: SCRRDEG_SUBJ_CODE
SCRRDEG_CRSE_NUMB
SCRRDEG_TERM_CODE_EFFECTIVE
SCRRDEG_REC_TYPE
SCRRDEG_ACTIVITY_DATE
SCRRDEG_DEGC_IND
SCRRDEG_DEGC_CODE
Fields: SCRRPRG_SUBJ_CODE
SCRRPRG_CRSE_NUMB
SCRRPRG_TERM_CODE_EFFECTIVE
SCRRPRG_REC_TYPE
SCRRPRG_ACTIVITY_DATE
SCRRPRG_PROGRAM_IND
SCRRPRG_PROGRAM
Fields: SCRRCAM_SUBJ_CODE
SCRRCAM_CRSE_NUMB
SCRRCAM_EFF_TERM
SCRRCAM_REC_TYPE
SCRRCAM_CAMP_IND
SCRRCAM_CAMP_CODE
SCRRCAM_ACTIVITY_DATE
Form:
SCABASE (owned by Registrar)
Fields: SCBCRKY_SUBJ_CODE
SCBCRKY_CRSE_NUMB
SCBCRKY_TERM_CODE_START
SCBCRKY_TERM_CODE_END
SCBCRKY_ACTIVITY_DATE
Form:
SCADETL (owned by Registrar)
Fields: SCREQIV_SUBJ_CODE
SCREQIV_CRSE_NUMB
SCREQIV_EFF_TERM
SCREQIV_SUBJ_CODE_EQIV
SCREQIV_CRSE_NUMB_EQIV
SCREQIV_START_TERM
SCREQIV_END_TERM
SCREQIV_ACTIVITY_DATE
Fields: SCRFEES_SUBJ_CODE
SCRFEES_CRSE_NUMB
SCRFEES_EFF_TERM
SCRFEES_DETL_CODE
SCRFEES_FEE_IND
SCRFEES_FEE_IND_IND
SCRFEES_FEE_AMOUNT
SCRFEES_ACTIVITY_DATE
SCRFEES_FTYP_CODE
Fields: SCRATTR_SUBJ_CODE
SCRATTR_CRSE_NUMB
SCRATTR_EFF_TERM
SCRATTR_ATTR_CODE
SCRATTR_ACTIVITY_DATE
Fields: SCBSUPP_SUBJ_CODE
SCBSUPP_CRSE_NUMB
SCBSUPP_EFF_TERM
SCBSUPP_TOPS_CODE
SCBSUPP_OCCS_CODE
SCBSUPP_CCSL_CODE
SCBSUPP_COOP_ED_IND
SCBSUPP_ACTIVITY_DATE
SCBSUPP_PERM_DIST_IND
SCBSUPP_CUDA_CODE
SCBSUPP_CUDB_CODE
SCBSUPP_CUDC_CODE
SCBSUPP_CUDD_CODE
SCBSUPP_CUDE_CODE
SCBSUPP_CUDF_CODE
SCBSUPP_CREDIT_CATEGORY_IND
Fields: SCBDESC_SUBJ_CODE
SCBDESC_CRSE_NUMB
SCBDESC_TERM_CODE_EFF
SCBDESC_ACTIVITY_DATE
SCBDESC_USER_ID
SCBDESC_TEXT_NARRATIVE
SCBDESC_TERM_CODE_END
Fields: SCRTEXT_SUBJ_CODE
SCRTEXT_CRSE_NUMB
SCRTEXT_EFF_TERM
SCRTEXT_TEXT_CODE
SCRTEXT_SEQNO
SCRTEXT_TEXT
SCRTEXT_ACTIVITY_DATE
Fields: SCRCORQ_SUBJ_CODE
SCRCORQ_CRSE_NUMB
SCRCORQ_EFF_TERM
SCRCORQ_SUBJ_CODE_CORQ
SCRCORQ_CRSE_NUMB_CORQ
SCRCORQ_ACTIVITY_DATE
Fields: SCRSBGI_SUBJ_CODE
SCRSBGI_CRSE_NUMB
SCRSBGI_EFF_TERM
SCRSBGI_SBGI_CODE
SCRSBGI_AGREEMENT_DATE
SCRSBGI_ACTIVITY_DATE
Form:
SCACRSE (owned by Registrar)
Fields: SCRLEVL_SUBJ_CODE
SCRLEVL_CRSE_NUMB
SCRLEVL_EFF_TERM
SCRLEVL_LEVL_CODE
SCRLEVL_ACTIVITY_DATE
Fields: SCRGMOD_SUBJ_CODE
SCRGMOD_CRSE_NUMB
SCRGMOD_EFF_TERM
SCRGMOD_GMOD_CODE
SCRGMOD_ACTIVITY_DATE
SCRGMOD_DEFAULT_IND
Fields: SCRSCHD_SUBJ_CODE
SCRSCHD_CRSE_NUMB
SCRSCHD_EFF_TERM
SCRSCHD_SCHD_CODE
SCRSCHD_ACTIVITY_DATE
SCRSCHD_WORKLOAD
SCRSCHD_MAX_ENRL
SCRSCHD_ADJ_WORKLOAD
SCRSCHD_INSM_CODE
Fields: SCRCPRT_SUBJ_CODE
SCRCPRT_CRSE_NUMB
SCRCPRT_TERM_CODE_EFF
SCRCPRT_ACTIVITY_DATE
SCRCPRT_USER_ID
SCRCPRT_PARS_CODE
SCRCPRT_PARS_PREF_NUMBER
Fields: SCRCRDF_SUBJ_CODE
SCRCRDF_CRSE_NUMB
SCRCRDF_TERM_CODE_EFF
SCRCRDF_ACTIVITY_DATE
SCRCRDF_USER_ID
SCRCRDF_RDEF_CODE
SCRCRDF_RDEF_PREF_NUMBER
Fields: SCBCRSE_SUBJ_CODE
SCBCRSE_CRSE_NUMB
SCBCRSE_EFF_TERM
SCBCRSE_COLL_CODE
SCBCRSE_DIVS_CODE
SCBCRSE_DEPT_CODE
SCBCRSE_CSTA_CODE
SCBCRSE_TITLE
SCBCRSE_CIPC_CODE
SCBCRSE_CREDIT_HR_IND
SCBCRSE_CREDIT_HR_LOW
SCBCRSE_CREDIT_HR_HIGH
SCBCRSE_LEC_HR_IND
SCBCRSE_LEC_HR_LOW
SCBCRSE_LEC_HR_HIGH
SCBCRSE_LAB_HR_IND
SCBCRSE_LAB_HR_LOW
SCBCRSE_LAB_HR_HIGH
SCBCRSE_OTH_HR_IND
SCBCRSE_OTH_HR_LOW
SCBCRSE_OTH_HR_HIGH
SCBCRSE_BILL_HR_IND
SCBCRSE_BILL_HR_LOW
SCBCRSE_BILL_HR_HIGH
SCBCRSE_APRV_CODE
SCBCRSE_REPEAT_LIMIT
SCBCRSE_PWAV_CODE
SCBCRSE_TUIW_IND
SCBCRSE_ADD_FEES_IND
SCBCRSE_ACTIVITY_DATE
SCBCRSE_CONT_HR_LOW
SCBCRSE_CONT_HR_HIGH
SCBCRSE_CONT_HR_IND
SCBCRSE_CEU_IND
SCBCRSE_REPS_CODE
SCBCRSE_MAX_RPT_UNITS
SCBCRSE_CAPP_PREREQ_TEST_IND
SCBCRSE_DUNT_CODE
SCBCRSE_NUMBER_OF_UNITS
Form:
SCAPREQ (owned by Registrar)
Fields: SCRRTST_SUBJ_CODE
SCRRTST_CRSE_NUMB
SCRRTST_TERM_CODE_EFF
SCRRTST_SEQNO
SCRRTST_TESC_CODE
SCRRTST_TEST_SCORE
SCRRTST_SUBJ_CODE_PREQ
SCRRTST_CRSE_NUMB_PREQ
SCRRTST_LEVL_CODE
SCRRTST_MIN_GRDE
SCRRTST_CONCURRENCY_IND
SCRRTST_CONNECTOR
SCRRTST_LPAREN
SCRRTST_RPAREN
SCRRTST_ACTIVITY_DATE
Table: SCRRARE
Fields: SCRRARE_SUBJ_CODE
SCRRARE_CRSE_NUMB
SCRRARE_TERM_CODE_EFFECTIVE
SCRRARE_ACTIVITY_DATE
SCRRARE_SEQNO
SCRRARE_AREA
Fields: SCBCRSE_SUBJ_CODE
SCBCRSE_CRSE_NUMB
SCBCRSE_EFF_TERM
SCBCRSE_COLL_CODE
SCBCRSE_DIVS_CODE
SCBCRSE_DEPT_CODE
SCBCRSE_CSTA_CODE
SCBCRSE_TITLE
SCBCRSE_CIPC_CODE
SCBCRSE_CREDIT_HR_IND
SCBCRSE_CREDIT_HR_LOW
SCBCRSE_CREDIT_HR_HIGH
SCBCRSE_LEC_HR_IND
SCBCRSE_LEC_HR_LOW
SCBCRSE_LEC_HR_HIGH
SCBCRSE_LAB_HR_IND
SCBCRSE_LAB_HR_LOW
SCBCRSE_LAB_HR_HIGH
SCBCRSE_OTH_HR_IND
SCBCRSE_OTH_HR_LOW
SCBCRSE_OTH_HR_HIGH
SCBCRSE_BILL_HR_IND
SCBCRSE_BILL_HR_LOW
SCBCRSE_BILL_HR_HIGH
SCBCRSE_APRV_CODE
SCBCRSE_REPEAT_LIMIT
SCBCRSE_PWAV_CODE
SCBCRSE_TUIW_IND
SCBCRSE_ADD_FEES_IND
SCBCRSE_ACTIVITY_DATE
SCBCRSE_CONT_HR_LOW
SCBCRSE_CONT_HR_HIGH
SCBCRSE_CONT_HR_IND
SCBCRSE_CEU_IND
SCBCRSE_REPS_CODE
SCBCRSE_MAX_RPT_UNITS
SCBCRSE_CAPP_PREREQ_TEST_IND
SCBCRSE_DUNT_CODE
SCBCRSE_NUMBER_OF_UNITS
Form:
PPAIDEN (owned by Human Resources)
Fields: SPRIDEN_PIDM
SPRIDEN_ID
SPRIDEN_LAST_NAME
SPRIDEN_FIRST_NAME
SPRIDEN_MI
SPRIDEN_CHANGE_IND
SPRIDEN_ENTITY_IND
SPRIDEN_ACTIVITY_DATE
SPRIDEN_USER
SPRIDEN_ORIGIN
SPRIDEN_SEARCH_LAST_NAME
SPRIDEN_SEARCH_FIRST_NAME
SPRIDEN_SEARCH_MI
SPRIDEN_SOUNDEX_LAST_NAME
SPRIDEN_SOUNDEX_FIRST_NAME
SPRIDEN_NTYP_CODE
SPRIDEN_CREATE_USER
SPRIDEN_CREATE_DATE
SPRIDEN_DATA_ORIGIN
Fields: PEBEMPL_PIDM
PEBEMPL_EMPL_STATUS
PEBEMPL_COAS_CODE_HOME
PEBEMPL_ORGN_CODE_HOME
PEBEMPL_COA_CODE_DIST
PEBEMPL_ORGN_CODE_DIST
PEBEMPL_ECLS_CODE
PEBEMPL_LCAT_CODE
PEBEMPL_BCAT_CODE
PEBEMPL_FIRST_HIRE_DATE
PEBEMPL_CURRENT_HIRE_DATE
PEBEMPL_ADJ_SERVICE_DATE
PEBEMPL_SENIORITY_DATE
PEBEMPL_LREA_CODE
PEBEMPL_LOA_BEG_DATE
PEBEMPL_LOA_END_DATE
PEBEMPL_TREA_CODE
PEBEMPL_TERM_DATE
PEBEMPL_I9_FORM_IND
PEBEMPL_I9_DATE
PEBEMPL_I9_EXPIRE_DATE
PEBEMPL_ACTIVITY_DATE
PEBEMPL_WKPR_CODE
PEBEMPL_FLSA_IND
PEBEMPL_STGR_CODE
PEBEMPL_DAYS_IN_CANADA
PEBEMPL_1042_RECIPIENT_CD
PEBEMPL_INTERNAL_FT_PT_IND
PEBEMPL_DICD_CODE
PEBEMPL_EGRP_CODE
PEBEMPL_IPEDS_SOFT_MONEY_IND
PEBEMPL_FIRST_WORK_DATE
PEBEMPL_LAST_WORK_DATE
PEBEMPL_CALIF_PENSION_IND
PEBEMPL_NRSI_CODE
PEBEMPL_SSN_LAST_NAME
PEBEMPL_SSN_FIRST_NAME
PEBEMPL_SSN_MI
PEBEMPL_SSN_SUFFIX
PEBEMPL_JBLN_CODE
PEBEMPL_COLL_CODE
PEBEMPL_CAMP_CODE
In order to have a better understanding of how these tables apply to our system, we have provided a couple of examples of information we would need. One example provides information for a department (to keep our information consistent, specifically the Computer Science Department), and one example will provide material from Banner for the Directory information of the catalog.
If we needed to retrieve course information for the Computer Science Department, we would be looking for information that would affect the SCACRSE, SCAPREQ, and SCADETL database forms. From the SCBCRSE table, which affects the SCACRSE form, we would need information such as SCBCRSE_CRSE_NUMB, SCBCRSE_TITLE, SCBCRSE_CREDIT_HR_IND, SCBCRSE_CREDIT_HR_LOW, SCBCRSE_CREDIT_HR_HIGH, SCBCRSE_LEC_HR_IND, SCBCRSE_LEC_HR_LOW, SCBCRSE_LEC_HR_HIGH, SCBCRSE_LAB_HR_IND, SCBCRSE_LAB_HR_LOW, SCBCRSE_LAB_HR_HIGH, SCBCRSE_OTH_HR_IND, SCBCRSE_OTH_HR_LOW, SCBCRSE_OTH_HR_HIGH, SCBCRSE_BILL_HR_IND, SCBCRSE_BILL_HR_LOW, SCBCRSE_BILL_HR_HIGH, SCBCRSE_REPEAT_LIMIT, SCBCRSE_CAPP_PREREQ_TEST_IND.
If we needed to retrieve course information for the Directory, we would be looking for listings of faculty, staff, administrators, and Board of Trustee members, to name a few. Therefore, we would need information from tables that affect the PPAIDEN forms. From the SPRIDEN table, we would need the following fields: SPRIDEN_LAST_NAME, SPRIDEN_FIRST_NAME, SPRIDEN_MI, SPRIDEN_CHANGE_IND, SPRIDEN_ENTITY_IND, SPRIDEN_USER, SPRIDEN_ORIGIN, SPRIDEN_DATA_ORIGIN.
It is possible that we will need more information from these tables than what we have listed, as we have not actually seen the tables and may need more fields provided within them upon actually seeing what is stored inside those fields.
1.6: Logical Format of Data Files and Databases
The information used to develop our catalog
will be stored in a database system. As
we have determined from information from our clients, the data needed to create
the college catalog are typically text documents, since text files are what is
sent to the catalog publisher. Also,
text files allows for easier editing for any users. Therefore, our database will have tables that
will store our information in text files.
As we have stated in the last section, we will
also need to copy Banner tables into our database, as Banner contains the most
up-to-date information about courses and faculty. The information that we retrieve from Banner
will also be stored in text format, allowing the entire document to be visible
within Microsoft Word, or any other word processing program.
2.1:
GUI Testing
Requirements Inventory
Design Inventory
The design inventory for testing is going to incorporate all of the different screens that will be used in the system. The system will use a different set of screens for different users. The type of screen the user would interact with will be determined by the permissions that each user is allotted. The first screen is the login screen. For this screen we will test that the system will log the user into its system and transfer the user to their proper section of the system.
Every screen that is involved in the system will have to be tested. These tests will include the obvious tests of all links and buttons on the screens. Besides those test, all pages will require specific tests. These tests will be used to make sure that the screens are able to submit the proper information to the database which is the principle software behind the system.
The other screens that will be tested are the catalog text editor pages. These pages will be tested to make sure that one side is read-only while the other side of the screen is a carbon copy with write access to make changes. This screen will consist of text editor software that is opened twice on the same screen. Also we will test the text editor to make sure that all changes are viewer friendly by changing the text color of edited material on the write-access side.
3.A: Gantt Chart
3.B:
Glossary of Terms
Access A relational database running under Microsoft Windows.
Browser An application program that
provides a way to look at and interact with all the information on the World
Wide Web.
Code Symbolic arrangement of data or instructions in a computer
program, or a set of such instructions.
Controlled
Decentralized An organizational structure for teams, in which a team
leader is defined, but all problem solving and decision-making is the
responsibility of the group.
Database An
information management system used for storing and retrieving related data.
Data Store Generic physical files that contain data necessary for the program, but which is external from the software developed.
Data flow diagram A representation of the functional
decomposition of a system.
Dreamweaver A
program used in the development of web pages.
Gantt Chart A
graphical-based, progressive timeline containing relevant dates, often used
with regard to planning and tracking a project.
GUI Graphical User
Interface: A user interface based on graphics (icons, pictures, and menus)
instead of text; uses a mouse as well as a keyboard as an input device.
HTML Hypertext Transfer
Markup Language: A markup language used to structure text and multimedia
documents and to set up hypertext links between documents, used extensively on
the World Wide Web.
Hypertext A computer-based text retrieval system that enables a
user to access particular locations in web pages or other electronic documents
by clicking on links within specific web pages or documents.
Internet An interconnected system of networks that connects
computers around the world via the TCP/IP protocol.
Java Script A
language used in the development of web pages.
Linear Sequential Model Sometimes called the classic life cycle or the waterfall model, this model, originally developed by W.W. Royce, suggests a systematic, sequential approach to software development that begins at the system level and progresses through analysis, design, coding, testing, and support.
mySQL
Open-Source database software
Network A network of data processing nodes that is interconnected for the purpose of data communication.
Open-Source A method and philosophy for software licensing and
distribution designed to encourage use and improvement of software by making
the code freely available.
Oracle A relational database management system that runs on most
mainframe, micro, and personal computers.
PHP PHP: Hypertext
Preprocessor (server-side scripting language).
Process An activity that changes or manipulates data.
Protocol A standard procedure for regulating data transmission
between computers.
Query A data retrieval request.
Relational Database A database system in which any database file
can be a component of more than one of the database's tables.
Software Written programs, procedures, or rules and associated
documentation pertaining to the operation of a computer system and that are
stored in read/write memory.
SQL Structured Query Language: A language
used in the creation and maintenance of databases.
Use Case Set of scenarios that show a usage of the system by a certain user.
User An individual that has signed onto a system and has been
assigned a user name and password.
Username A system created login for users.
Universal User Any person, whether directly or indirectly involved with the system, who has the ability to perform certain functions. In the case of the Siena College Catalog Project, any universal user has the ability to view the Siena College Catalog via the Internet.
Visual Basic A popular event-driven visual programming system from Microsoft
Corporation for Microsoft Windows.
Web-based Uses the World Wide Web (via HTML) on the Internet to gain access to the system.